Systems and methods for providing uniform access in a multi-tenant system

ABSTRACT

Receive, by a central controller engine, a user request to perform one or more operations associated with user data, wherein the user data includes first data and second data. Select, by the central controller engine based on the user request, a first service provider interface (SPI) integrated into a first service, the first SPI being configured to operate on the first data in a first datastore associated with the first service. The first SPI including a first service interface component configured based on a uniform access specification. Obtain, by the first SPI, the first data, the first data being formatted according to a first service data specification. Transform, by the first SPI based on the uniform access specification, the first data, thereby generating transformed first data formatted according to the uniform access specification. Provide, by the first SPI, the transformed first data to a target service.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. Nonprovisional patent application Ser. No. 16/431,544, filed Jun. 4, 2019 and entitled “Systems and Methods for Providing Uniform Access In A Multi-Tenant System,” which claims the benefit of U.S. Provisional Patent Application Ser. 62/680,559, filed Jun. 4, 2018 and entitled “Multi-Tenant System for Providing Uniform Access,” which are hereby incorporated by reference herein. The present application also incorporates by reference U.S. Nonprovisional application Ser. No. 16/431,517, entitled “Systems and Methods for Providing Error Recovery in Data Transmissions” and U.S. Nonprovisional application Ser. No. 16/432,663, entitled “Multi-Tenant System for Providing Arbitrary Query Support”, both of which were filed on Jun. 4, 2019.

TECHNICAL FIELD

This disclosure pertains to multi-tenant computing systems. More specifically, this disclosure pertains to providing uniform access in multi-tenant computing systems.

BACKGROUND

Under conventional approaches, a data layer may provide different application programming interfaces (APIs) for accessing disparate data sources. For example, a data layer may include fifty different APIs for accessing fifty different data sources However, such conventional data layers are typically difficult to implement and/or maintain, and they do not effectively scale. For example, changes to the data sources typically breaks the layer and/or API(s) of the layer.

SUMMARY

A claimed solution rooted in computer technology overcomes problems specifically arising in the realm of computer technology. In various embodiments, a multi-tenant computing system (or, simply, multi-tenant system) is configured to receive a user request. The user request may be a request initiated by a tenant (e.g., Verizon) of the multi-tenant system to obtain some or all of their tenant data. For example, the tenant data may include usage data stored in a usage datastore managed by a usage service of the multi-tenant system. The tenant data may also include subscription data stored in a subscription datastore managed by a subscription service of the multi-tenant system. The “services” described herein may be microservices, and/or the services may function and/or be defined differently. For example, the usage service may store and/or access data in one manner (e.g., as defined by a specification for the usage service), and the subscription service may store and/or access data in another manner (e.g., as defined by a specification for the subscription service). In order for the multi-tenant system to access the different services, and/or the data associated with those services, in a uniform manner, each of the services may include a service provider interface. In some embodiments, the multi-tenant system may provide the same service provider interface to each of the different services, and the service provider interfaces may only require minimal modification to function with a particular service. For example, the modification may include defining locations of datastores and/or data formats for the datastore (e.g., object-based, relational, flat-file). Accordingly, modifying the service provider interface for a particular service may only include adding or modifying two or three lines of code within the service provider interface. The remaining portions of the service provider interface may be common across all of the service provider interface for the various services of the multi-tenant system.

In some embodiments, each of the service provider interfaces may be defined by the multi-tenant system according to a uniform access specification. For example, the uniform access specification may define a format for data output from services, a format for data input to services, and/or the like. In this manner, requests may be provided to services in a uniform manner, and data may be consumed from services in a uniform manner, regardless of how the services handle that data within the services themselves (and/or the datastores associated with the services). This solution may be more scalable than traditional solutions, for example, at least because the service provider interfaces may be maintained by their respective services and/or associated development teams. The multi-tenant system may provide requests and consume data in a uniform manner, without having to maintain a large “glue layer” that is implemented independent of the services. As more services are added, the same service provider interfaces may be deployed, and then implemented by the added services with minimal modification.

Various embodiments of the present disclosure include systems, methods, and non-transitory computer readable media configured to receive, by a central controller engine, a user request to perform one or more operations associated with user data, wherein the user data includes first data and second data. Select, by the central controller engine based on the user request, a first service provider interface (SPI) integrated into a first service, the first SPI being configured to operate on the first data in a first datastore associated with the first service, the first SPI including a common interface component configured to facilitate communication between the central controller engine and the first SPI, and the first SPI including a first service interface component configured based on a uniform access specification. Obtain, by the first service using the first SPI, at least a portion of the first data from the first datastore associated with the first service, the at least a portion of the first data being formatted according to a first service data specification. Transform, by the first SPI based on the uniform access specification, the at least a portion of the first data, thereby generating transformed first data formatted according to the uniform access specification. Provide, by the first service using the first SPI, the transformed first data to a target service.

In some embodiments, the systems, methods, and non-transitory computer readable media further configured to select, by the central controller engine based on the user request, a second service provider interface (SPI) integrated into a second service, the second SPI being configured to operate on the second data in a second datastore associated with the second service, the second SPI including the common interface component configured to facilitate communication between the central controller engine and the second SPI, and the second SPI including a second service interface component configured based on the uniform access specification; obtain, by the second service using the second SPI, at least a portion of the second data from the second datastore associated with the second service, the at least a portion of the second data being formatted according to a second service data specification; transform, by the second SPI based on the uniform access specification, the at least a portion of the second data, thereby generating transformed second data formatted according to the uniform access specification; and provide, by the second service using the second SPI, the transformed second data to the target service.

In some embodiments, the user data comprises tenant data, the first data comprises usage data, and the second data comprises subscription data

In some embodiments, the first service comprises a usage service, and the second service comprises a subscription service.

In some embodiments, the central controller engine comprises a different service from the target service.

In some embodiments, the central controller engine comprises the target service.

In some embodiments, the systems, methods, and non-transitory computer readable media are further configured to store, by the central controller engine, a first state of the first service; store, by the central controller engine, a second state of the second service; determine, by central controller engine, a failure of the first service; and relaunch, by the central controller engine in response to the determining the failure of the first service, the first service based on the stored first state of the first service.

In some embodiments, the systems, methods, and non-transitory computer readable media further configured to determine, by central controller engine, a failure of the second service; and relaunch, by the central controller engine in response to the determining the failure of the second service, the second service based on the stored second state of the second service.

In some embodiments, the providing, by the first service using the first SPI, the transformed first data to a target service, comprises streaming, by a common communication component of the first service using the first SPI, the transformed first data to the first target service; and wherein the providing, by the second service using the second SPI, the transformed second data to a second target service, comprises streaming, by a common communication component of the second service using the first SPI, the transformed second data to the second target service, the common communication component of the first service being the same as the common communication component of the second service.

These and other features of the systems, methods, and non-transitory computer readable media disclosed herein, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for purposes of illustration and description only and are not intended as a definition of the limits of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a diagram of an example network system for providing cloud-based software-as-a-service (SAAS) services of a multi-tenant system to multiple tenants according to some embodiments of the present invention.

FIG. 2 depicts a diagram of an example portion of a multi-tenant system for enabling uniform access to data in disparate datastores and/or disparate services according to some embodiments.

FIG. 3 depicts a diagram of an example service provider interface (SPI) according to some embodiments.

FIG. 4A depicts a diagram of an example export process using an example central controller engine and an example service provider interface (SPI) of an example portion of a multi-tenant system according to some embodiments.

FIG. 4B depicts a diagram of an example import process using an example central controller engine and an example service provider interface (SPI) of an example portion of a multi-tenant system according to some embodiments.

FIG. 5A-B depict a flowchart of an example of a method of providing uniform access in a multi-tenant system according to some embodiments.

FIG. 6 is a diagram of an example computer system for implementing the features disclosed herein according to some embodiments.

DETAILED DESCRIPTION

A claimed solution rooted in computer technology overcomes problems specifically arising in the realm of computer technology. In various embodiments, a multi-tenant computing system (or, simply, multi-tenant system) is configured to receive a user request. The user request may be a request initiated by a tenant (e.g., Verizon) of the multi-tenant system to obtain some or all of their tenant data. For example, the tenant data may include usage data stored in a usage datastore managed by a usage service of the multi-tenant system. The tenant data may also include subscription data stored in a subscription datastore managed by a subscription service of the multi-tenant system. The “services” described herein may be microservices, and/or the services may function and/or be defined differently. For example, the usage service may store and/or access data in one manner (e.g., as defined by a specification for the usage service), and the subscription service may store and/or access data in another manner (e.g., as defined by a specification for the subscription service). In order for the multi-tenant system to access the different services, and/or the data associated with those services, in a uniform manner, each of the services may include a service provider interface. In some embodiments, the multi-tenant system may provide the same service provider interface to each of the different services, and the service provider interfaces may only require minimal modification to function with a particular service. For example, the modification may include defining locations of datastores and/or data formats for the datastore (e.g., object-based, relational, flat-file). Accordingly, modifying the service provider interface for a particular service may only include adding or modifying two or three lines of code within the service provider interface. The remaining portions of the service provider interface may be common across all of the service provider interface for the various services of the multi-tenant system.

In some embodiments, each of the service provider interfaces may be defined by the multi-tenant system according to a uniform access specification. For example, the uniform access specification may define a format for data output from services, a format for data input to services, and/or the like. In this manner, requests may be provided to services in a uniform manner, and data may be consumed from services in a uniform manner, regardless of how the services handle that data within the services themselves (and/or the datastores associated with the services). This solution may be more scalable than traditional solutions, for example, at least because the service provider interfaces may be maintained by their respective services and/or associated development teams. The multi-tenant system may provide requests and consume data in a uniform manner, without having to maintain a large “glue layer” that is implemented independent of the services. As more services are added, the same service provider interfaces may be deployed, and then implemented by the added services with minimal modification.

FIG. 1 depicts a diagram of an example network system 100 for providing cloud-based software-as-a-service (SAAS) services of a multi-tenant system 102 to multiple tenants according to some embodiments. Examples of the cloud-based SAAS services include data storage, data processing, and business-oriented applications. In some embodiments, each tenant may be a subscription-based entity or provider (e.g., an internet service provider, a home security system and service provider, a cellular phone service provider, or entertainment content provider). Each tenant may include a group of one or more users (e.g., individuals, business entities, customers of the business entities, systems) who share access to the cloud-based services. In one embodiment, a tenant includes a service entity such as AT&T, Netflix, Verizon, and/or the like. A tenant may include one or more products or services of an entity. For example, AT&T internet products may be a particular tenant, and AT&T security products may be another tenant. In some embodiments, the cloud-based SAAS services relate to managing subscriber records, product and/or service consumption information, billing information, payment information, and/or the like.

The network system 100 includes the multi-tenant system 102 coupled via a data network 104 (e.g., a set of one or more public and/or private, wired and/or wireless networks) to client devices 106. The multi-tenant system 102 includes shared resources to host the cloud-based SAAS services to the tenants. The shared resources may include processors, memory, virtual systems, services, application programs, load balancers, firewalls, and/or the like. As shown, the multi-tenant system 102 includes tenant interfaces 110, server systems 112, and datastores 114. Each of the client devices 106 includes a client system 108 that accesses the cloud-based SAAS services hosted by the multi-tenant system 102. In some embodiments, the client systems 108 may be operated by employees (e.g., administrator users) of the provider of the provider of the multi-tenant system 102. In some embodiments, the client systems 108 may be operated by employees of the tenant. In some embodiments, the client systems 108 may be operated by end users of the tenant's services.

Each client device 106 may include a desktop, laptop, notebook, tablet, personal digital assistant, smart phone, or other consumer electronic devices incorporating one or more computer components. The client system 108 on each client device 106 may include hardware, software and/or firmware for communicating with the multi-tenant system 102 and accessing the cloud-based services it hosts. Examples of the client systems 108 may include web browsers, client engines, drivers, user interface components, proprietary interfaces, and/or the like.

The multi-tenant system 102 includes hardware, software and/or firmware to host the cloud-based services for the tenants. It will be appreciated that the typical multi-tenant system 102 may offer access to shared resources including systems and applications on shared devices and offer each tenant the same quality or varying qualities of service. In some embodiments, the multi-tenant system 102 does not use virtualization or instantiation processes. In some embodiments, a multi-tenant system 102 integrates several business computing systems into a common system with a view toward streamlining business processes and increasing efficiencies on a business-wide level.

In some embodiments, the multi-tenant system 102 includes a user interface tier of multiple tenant interfaces 110, a server tier of multiple server systems 112, and a datastore tier of multiple datastores 114 for the multiple tenants. In some embodiments, the tenant interfaces 110 includes graphical user interfaces and/or web-based interfaces to enable tenants to access the shared services hosted by the multi-tenant system 102. The tenant interfaces 110 may support load balancing when multiple tenants (and/or multiple customers of the tenants) try to access the multi-tenant system 102 concurrently. The tenant interfaces 110 may additionally or alternatively include an operator interface for use by a systems operator to configure or otherwise manage the multi-tenant system 102. In some embodiments, each tenant may be associated with a subset of the total tenant interfaces 110 for load balancing.

In some embodiments, the server systems 112 include hardware, software and/or firmware to host the shared services for tenants. The hosted services may include tenant-specific business services or functions, including enterprise resource planning (ERP), customer relationship management (CRM), eCommerce, Human Resources (HR) management, payroll, financials, accounting, calendaring, order processing, subscription billing, inventory management, supply chain management (SCM), collaboration, sales force automation (SFA), marketing automation, contact list management, call-center support, web-based customer support, partner and vendor management systems, product lifecycle management (PLM), financial, reporting and analysis, and/or the like. Similar to the tenant interfaces 110, in some embodiments, the server systems 110 may support load balancing when multiple tenants (and/or multiple customers of tenants) try to access the multi-tenant system 102 concurrently. Further, in some embodiments, each tenant may be associated with a subset of the total server systems 112 for load balancing.

In some embodiments, tenant data 120 for each tenant may be stored in a logical store across one or more datastores 114. In some embodiments, each tenant uses a logical store that is not assigned to any predetermined datastores 114. Each logical store may contain tenant data 120 that is used, generated and/or stored as part of providing tenant-specific business services or functions. In some embodiments, the datastores 114 may include relational database management systems (RDBMS), object-based database systems, and/or the like. In some embodiments, tenant data 120 may be stored across multiple datastores 114, with each datastore dedicated to a particular service (e.g., managing customer records, managing product and/or service consumption information, managing billing information, managing payment information, and/or the like).

In some embodiments, the tenant data 120 may include subscription information, such as billing data and/or subscription status (e.g., active, canceled, suspended, re-activated). Billing data may include billing invoice data (e.g., date of invoices and invoice amounts, overage charge dates and overage charge amounts), payment transaction data (e.g., date of payments, amount of payments), payment methods (e.g., credit card, debit card), payment plan (e.g., annual billing, monthly billing), and/or service plan information (e.g., the name of a service plan). Subscription information may also include a geographic region and/or location associated with a tenant, service, and/or subscriber. In some embodiments, the tenant data 120 may include usage data (e.g., account activity data), such as new subscriptions, changes to subscribed products and/or services, cancellation of one or more products and/or services, subscriptions to new products and/or services, application of discounts, loyalty program package changes (e.g., additional programs and/or services, special rates, and/or the like for loyal customers), reduction or increase of rates for products and/or services, and/or cancellation of the application. In some embodiments, account activity may include usage of a product and/or product of a subscriber (e.g., what channels the subscriber actually watches, what services and what level of consumption the subscriber receives, quality of the product and/or services, and/or the like).

In some embodiments, the tenant data 120 may be stored in one or more data formats (or, simply, formats). For example, subscription tenant data may be stored in a particular format, and usage tenant data may be stored in another format. As used herein, formats may include data types, variable types, protocols (e.g., protocols for accessing, storing, and/or transmitting data), programming languages, scripting languages, data value parameters (e.g., date formats, string lengths), endpoint locations and/or types, and/or the like.

In some embodiments, the multi-tenant system 102 functions to provide uniform access to disparate services (e.g., microservices) and/or disparate datastores. For example, different services of the multi-tenant system 102 may manage (e.g., create, read, update, delete) tenant data 120 stored in different datastores 114. It will be appreciated that as used herein, a “service” may be single service and/or a set of services (e.g., a cluster of services). The datastores 114 may store data in different formats, and/or the services may handle data differently. The services may each include a service provider interface (SPIs) that provides data from the service, and/or receives data at the service, in a common (or, uniform) format, regardless of the original format that may be used by the service and/or datastores 114. In some embodiments, the multi-tenant system 102 may define a uniform access specification that defines the common format that the services must comport with when receiving and/or providing data. For example, each service may include a service provider interface, and communication with the service may be performed through the service provider interface. Accordingly, each of the services may be accessed in a uniform manner, and data may be consumed from the services in a uniform manner, regardless of the internal specifications and/or operations of the service.

The data network (or, communication network) 104 may represent one or more computer networks (e.g., LAN, WAN, or the like) or other transmission mediums. The data network 104 may provide communication between the systems, engines, datastores, components, and/or devices described herein. In some embodiments, the data network 104 includes one or more computing devices, routers, cables, buses, and/or other network topologies (e.g., mesh, and the like). In some embodiments, the data network 104 may be wired and/or wireless. In various embodiments, the data network 104 may include the Internet, one or more wide area networks (WANs) or local area networks (LANs), one or more networks that may be public, private, IP-based, non-IP based, and so forth.

FIG. 2 depicts a diagram of an example portion 200 of a multi-tenant system 102 for enabling uniform access to data in disparate datastores 114 and/or disparate services 206 according to some embodiments. In the example of FIG. 2, the example portion 200 of the multi-tenant system 102 includes a central controller engine 202, network devices 204, services 206 a to 206 c (individually, the service 206, collectively, the services 206), service provider interfaces (SPIs) 208 (individually, the service provider interface 208, collectively, the service provider interfaces 208), and datastores 114 a to 114 c (individually, the datastore 114, collectively, the service provider datastores 114). The three datastores 114 may each be respectively managed by the three sets of one or more services 206, and each respectively made accessible in a uniform manner by the service provider interfaces (SPIs) 208. In some embodiments, the central controller engine 202, which may support internal or tenant communications, is coupled via network devices 204 with the datastores 114. The network devices 204 may include routers, load balancers, firewalls, and/or the like. Although only three services 206, three service provider interfaces 208, and three datastores 114 are shown here, it will be appreciated that the multi-tenant system 102 may support a greater or lesser number of such services 206, service provider interfaces 208, and/or datastores 114.

As discussed herein, the multi-tenant system 102 distributes tenant data across multiple datastores 114 at multiple locations. As shown, the multi-tenant system distributes tenant data across at least datastores 114 a, 114 b and 114 c. The multi-tenant system 102 may include one or more services, shown as services 206 a, 206 b and 206 c, to respectively manage the tenant data at each datastore 114 through one or more application program interfaces (APIs). APIs are typically designed to be specific to the purpose of the service it supports and may differ widely in the exposed capabilities and performance. For example, in some systems, each of the different datastores 114 and each of the different services 206 may be developed independently of one another and possibly by different development teams. Accordingly, it is common that the API calls are non-uniform.

To solve the nonuniformity, the system could incorporate a “glue” layer, e.g., an enterprise service bus or a service-oriented architecture (SOA layer) that access data via the APIs and exposes it to the consumers. Glue layers typically access data directly from the datastore, bypassing the services with their different APIs. Glue layers have been found to be brittle, needing to be matched continuously to changing APIs that the services expose. Further, direct database access often violates data integrity guarantees or service level agreements that a service is trying to offer. Further, data exposed directly from the database often has a different shape than the data exposed at API level. Data exposed directly from the database therefore requires extensive transformation to match the data shape of that received at the API level. API enforcement through code or process is often inconsistent, which often results in multiple incompatible implementations. By putting these requirements on the software development process, the resulting APIs may only be “lowest common denominator” APIs instead of matching the desired use cases for the services.

To enable uniform access to the services 206 and the tenant data 120 stored in the datastores 114, in some embodiments, the multi-tenant system 102 includes a software component embedded directly (or, integrated) into the services 206. In other embodiments, the software component may be hooked into the services 206, as opposed to embedded directly into the services 206. This software component, referred to herein as a service provider interface (SPI) 208 a, 208 b and 208 c respectively, may be delivered as a library to a service development team for integration into the services 206 to make their services compatible, without having to change their APIs or expose internal details of their database. With the service provider interface 208 integrated into the services 206, the multi-tenant system 102 enables access to diverse data services in a uniform manner without having to build extensive glue layers between services, the consumers, and/or other features of the multi-tenant system 102. Each of the services 206 may enable access to the diverse data services without exposing their internal data organization and/or without bypassing the services 206. Development teams can use the service provider interfaces 208 to allow access to the data exposed by the services 206 in a uniform manner, and also provide data in a uniform manner, regardless of the internal formats and specification used by the service.

In the example of FIG. 2, the central controller engine 202 includes a job invocation component 202 a, a polling component 202 b, a job management component 202 c. The job invocation component 202 a may function to receive user requests (or, tenant requests). User requests may include export requests, import requests, and/or the like. For example, a request may include a request from a tenant to obtain some or all of the their tenant data 120. User requests may be received in a variety of different formats. For example, requests may be obtained in tenant formats (e.g., a Verizon format, an AT& format).

In some embodiments, the job invocation component 202 a may function to identify and/or select service provider interfaces 208. In some embodiments, the job invocation component 202 a may function to identify and/or select service provider interfaces 208 based on user requests. For example, the job invocation component 202 a may store a topology of the services (e.g., in a file stored in the controller datastore 203). The topology of the services may also be maintained by another service, and the job invocation component 202 a may query that other service for a current topology. The topology may indicate locations (e.g., an endpoint location) of service provider interfaces 208 and/or services 206. In some embodiments, the job invocation component 202 a may parse a user request, and identify the services 206 to process the request based on the topology. For example, the job invocation component 202 a may parse an extract request for usage data and subscription data, and identify the location of the service provider interface 208 for the usage service based on the topology, and the location of the service provider interface 208 for the subscription service based on the topology.

In some embodiments, the job invocation component 202 a functions to provide (e.g., generate and/or transmit) service requests. For example, the job invocation component 202 a may provide a service request based on a user request and a selected service provider interface 208. In some embodiments, the service request may be in a common format. For example, the job invocation component 202 a may provide service requests based on a uniform access specification. The uniform access specification may define one or more common protocols, data formats, programming languages, endpoints, and/or the like, for communication between the services 206, the central controller engine 202, and/or other elements of the multi-tenant system 102. For example, the uniform access specification may define output format requirements for data output from the services 206, and input format requirement for the services 206.

In some embodiments, the job invocation component 202 a functions to receive and/or provide information (e.g., in addition to user requests and/or service requests). For example, the job invocation component 202 a may receive a request result, and provide the request results to another system and/or user (e.g., a tenant user). The request results may be in a common format (e.g., based on the service provider interface 208 and/or uniform access specification), regardless of which service 206 provided to the data. For example, a request result may include usage data and subscription data in a common format.

The polling component 202 b may function to query services 206 to determine a status of jobs (e.g., service requests) and/or services 206. A status may include a completion status (e.g., 56% complete) of a job, and/or whether the service 206 is responsive or has timed-out. For example, the polling component 202 b may query (e.g., poll) a usage service 206 to the determine the status of a request to obtain (e.g., fetch, pull, push) usage data for a particular tenant of the multi-tenant system 102. The polling component 202 b may determine if a service has failed if query attempt fail.

The job management component 202 c may function to maintain state information (or, simply, “state”) of jobs, services 206, and/or the central controller engine 202. This may be more resilient than maintaining states at each of the services, and avoid having to perform state reconciliation. In some embodiments, the job management component 202 c may store state information in the controller datastore 203. For example, state information may include the associated service request, a status of the service status, a status of the service request, and/or the like. If a service has failed (e.g., as determined by the polling component 202 b), the job management component 202 c may relaunch the failed according to the state information. Similarly, if the central controller engine 202 has recently relaunched (e.g., in response to failure of the central controller engine 102), the job management component 202 c may relaunch services based on the state information.

FIG. 3 depicts a diagram of an example service provider interface (SPI) 208 according to some embodiments. Generally, under some approaches (e.g., approaches that do not use service provider interfaces 208), services typically needed to receive information (e.g., service requests) in a format native to the particular service and/or associated datastores. Accordingly, information typically had to be provided in different formats for different services. Alternatively, under other approaches that do not use service provider interfaces 208, the entity providing the request for information, and/or receiving a response to the request for information, had to translate the requests prior to sending the request, and/or translate the responses after they have been sent from the service. The service provider interface 208 may allow information to be provided (e.g., from the requesting entity) to different services in a common format (e.g., based on a uniform access specification and/or service data specifications of the services), and/or may allow information to be provided from the different services in a common format (e.g., based on a uniform access specification and/or service data specifications of the services).

In the example of FIG. 3, the service provider interface 208 includes a service interface component 302, a common interface component 304, a serialization support component 308, an encryption component 310, a file format component 312, and a communication component 314. The service interface component 302 may function to facilitate implementation of uniform access for a particular service 208. While the other components (e.g., components 304-312) of the service provider interface 208 may be common across all of the service provider interfaces 208, the service interface component 302 may be modified for the particular service 208. In some embodiments, services 208 may be implemented and/or managed by different development teams. For example, a usage service 208 may be managed by a usage development team, a subscription service 208 may be managed by a subscription development team, and so forth. The different services 208 may adhere to different service data specifications. For example, a usage service 208 may store and/or access data according to a first format (e.g., data format, access protocols), and a subscription service 208 may store and/or access data according to another format (e.g., another data format, another access protocol). The service interface component 302 may provide the instructions for processing requests received in a common format, and/or providing responses to such requests in a common format. For example, the service interface component 302 may translate requests received according to a common format into a request that can be processed by a service that is formatted according to a specific data specification of that service. More specifically, for example, the common request may include variable for various parameters (e.g., access protocol types, data format types, endpoint locations, and/or the like), and the service interface component 302 may define the values for those variables.

In some embodiments, the service interface component 302 of a service provider interface may be deployed (e.g., to a particular service) with a template service interface component, which may be modified (e.g., by the particular service) based on the service data specification of the particular service.

The common interface component 304 may function to receive information (e.g., service requests) in a common format, and/or provide information (e.g., services request results) in a common format (e.g., to the central controller engine 202). The common interface component 304 may be the same (e.g., having the same source code, object code, machine code, and/or the like) as the common interface components 304 of the other service provider interfaces 208 of the other services 206. In some embodiments, the common interface component 304 may comprise a REST interface. The common interface component 304 may be defined and/or function according to the uniform access specification.

The serialization support component 306 may function to provide serialization and/or deserialization support. The serialization support component 306 may include instructions (e.g., code) to convert one or more objects (e.g., one or more data records, between a sequence of bytes that can be sent through streams). The serialization support component 306 may be the same (e.g., having the same source code, object code, machine code, and/or the like) as the serialization support components 306 of the other service provider interfaces 208 of the other services 206, and may not require any modification (e.g., by the service development team) to function with the associated service 206. The serialization support component 306 may be defined and/or function according to the uniform access specification.

The encryption component 308 may function to encrypt communication with other elements in the multi-tenant system 102. For example, the encryption component 208 may encrypt data imported in the service provider interface 208 and/or data exported from the service provider interface 208. For example, a target location for exported data may require a particular encryption, and the encryption component 308 may ensure data is encrypted properly prior to exporting to the target location. The encryption component 308 may be the same (e.g., having the same source code, object code, machine code, and/or the like) as the encryption components 308 of the other service provider interfaces 208 of the other services 206, and may not require any modification (e.g., by the service development team) to function with the associated service 206. The encryption component 308 may be defined and/or function according to the uniform access specification.

The file format component 310 may function to facilitate data record formatting. For example, the file format component 310 may format data as JSON objects, CSV files, and/or custom types. The file format component 310 may be the same (e.g., having the same source code, object code, machine code, and/or the like) as the file format component 310 of the other service provider interfaces 208 of the other services 206, and may not require any modification (e.g., by the service development team) to function with the associated service 206. The file format component 310 may be defined and/or function according to the uniform access specification.

The communication component 312 may function to provide (e.g., stream, upload) data. For example, the communication component 312 may function to provide data to an S3 bucket. The communication component 312 may be the same (e.g., having the same source code, object code, machine code, and/or the like) as the communication components 312 of the other service provider interfaces 208 of the other services 206, and may not require any modification (e.g., by the service development team) to function with the associated service 206. The communication component 312 may be defined and/or function according to the uniform access specification.

FIG. 4A depicts a diagram of an example export process 400 using an example central controller engine 202 and an example service provider interface (SPI) 208 of an example portion of a multi-tenant system 102 according to some embodiments. As shown, an export request 406 is provided to the central controller engine 202 via its API 404. The central controller engine 202 generates a uniform export request using a uniform call to the common interface component 304 of the SPI 208. The SPI 208 generates the SPI-level export request, which the UsageExporter module 418 of the usage service 414 manages by reading tenant data 120 from the usage database 114 and exporting data 416 (e.g., encrypted and/or otherwise formatted/transformed according to the service provider interface 208 and/or associated uniform access specification). Because the usage service 208 includes a usage service provider interface 208, the export request can be uniform (e.g., having the same format as requests to other services), and/or the exported data can be uniform (e.g., having the same format as data exported from other services).

FIG. 4B depicts a diagram of an example import process 401 using an example central controller engine and an example service provider interface (SPI) of an example portion of a multi-tenant system 102 according to some embodiments. As shown, an import request 422 is provided to the central controller engine 202 via its API 404. The central controller engine 202 generates a uniform import request using a uniform call to the common interface component 204 of the SPI 208. The SPI 208 generates the SPI-level import request, which the UsageImporter module 410 of the usage service 208 manages by writing tenant data 120 to the usage database 114 in a format of the datastore 112 and/or the usage service 208. Because the usage service includes an SPI 208, the import request can be uniform (e.g., having the same format as requests to other services), and/or the imported data can be uniform (e.g., having the same format as data exported from other services) when received by the service provider interface 208, but stored in the datastore 112 in the format of the datastore 112.

FIG. 5A-B depict a flowchart of an example of a method 500 of providing uniform access in a multi-tenant system according to some embodiments. In this and other flowcharts and/or sequence diagrams, the flowchart illustrates by way of example a sequence of steps. It should be understood the steps may be reorganized for parallel execution, or reordered, as applicable. Moreover, some steps that could have been included may have been removed to avoid providing too much information for the sake of clarity and some steps that were included could be removed, but may have been included for the sake of illustrative clarity.

In step 502, an multi-tenant system (e.g., multi-tenant system 102) receives a user request (e.g., export request 406) to perform one or more operations (e.g., export operations) associated with user data (e.g., tenant data 120). The user request may be received in a first format (e.g., a propriety format, such as a Verizon format). The user data may include first data (e.g., usage data) and second data (e.g., subscription data). In some embodiments, a central controller engine (e.g., central controller engine) receives the user request. In some embodiments, an application programming interface (e.g., API 404) of the central controller engine receives the user request.

In step 504, the multi-tenant system selects a first service provider interface (e.g., service provider interface 208 a) integrated into a first service (e.g., service 208 a). The first service may be a usage service. The first service provider interface may be configured to operate on the first data in a first datastore (e.g., datastore 114 a) associated with the first service. The first service provider interface may include a common interface component (e.g., common interface component 304) configured to facilitate communication between the central controller engine and the first service provider interface. The first service provider interface may include a first service interface component (e.g., service interface component 302) configured based on a uniform access specification. In some embodiments, the central controller engine selects the first service provider interface. In some embodiments, a job invocation component (e.g., job invocation component 202 a) of the central controller engine selects the first service provider interface.

In some embodiments, the central controller engine 202 provides (e.g., generates, transmits) a service request to the first service provider interface based on the user request. For example, the job invocation component may generate a service request in a second format (e.g., a common format) from the user request. The job invocation component may transmit the service request to the common interface component of the service provider interface.

In step 506, the multi-tenant system obtains at least a portion of the first data from the first datastore associated with the first service. The at least a portion of the first data may be formatted according to a first service data specification. In some embodiments, the first service may use the first service provider interface to obtain the data from the first datastore.

In step 508, the multi-tenant system transforms the at least a portion of the first data, thereby generating transformed first data (e.g., encrypted data 416) formatted according to the uniform access specification. In some embodiments, one or more components of the first service provider interface transforms the data, such as the service interface component, an encryption component (e.g., encryption component 308), a serialization support component (e.g., serialization support component 304), and/or a file format component (e.g., file format component 310). In some embodiments, the data is transformed based on the uniform access specification.

In step 510, the multi-tenant system provides the transformed first data to a target service. For example, the target service may be part of the central controller engine and/or it may be another service. In some embodiments, a common communication component (e.g., communication component 312) of the first service provider interface streams the transformed data to the target service.

In step 512, the multi-tenant system selects a second service provider interface (e.g., service provider interface 208 b) integrated into a second service (e.g., service 206 b). The second service may be a subscription service. The second service provider interface may be configured to operate on the second data in a second datastore (e.g., datastore 114 b) associated with the second service. The second service provider interface may include the common interface component configured to facilitate communication between the central controller engine and the second service provider interface. In other words, the common interface component of the second service provider interface may be the same (e.g., having the same source code, object code, machine code, and/or the like) as the common interface component of the first service provider interface. The second service provider interface may include a second service interface component configured based on the uniform access specification. In other words, the second service interface component may different same (e.g., having different source code, object code, machine code, and/or the like) from the first service provider interface. For example, the first service interface component may be based on a first service data specification, and the second service interface component may be based on the second service data specification. In some embodiments, the central controller engine of the multi-tenant system selects the second service provider interface. In some embodiments, the job invocation component of the central controller engine selects the second service provider interface.

In some embodiments, the central controller engine 202 provides (e.g., generates, transmits) a second service request to the second service provider interface based on the user request. For example, the job invocation component may generate a second service request in a second format (e.g., a common format) from the user request. The job invocation component may transmit the second service request to the common interface component of the second service provider interface.

In step 514, the multi-tenant system obtains at least a portion of the second data from the second datastore associated with the second service. The at least a portion of the second data may be formatted according to a second service data specification. In some embodiments, the second service obtains the second data using the second service provider interface.

In step 516, the multi-tenant system transforms the at least a portion of the second data, thereby generating transformed second data formatted according to the uniform access specification. In some embodiments, one or more components of the second service provider interface transforms the second data, such as the service interface component of the second service provider interface, an encryption component (e.g., encryption component 308) of the second service provider interface, a serialization support component (e.g., serialization support component 304) of the second service provider interface, and/or a file format component (e.g., file format component 310) of the second service provider interface. In some embodiments, the data is transformed based on the uniform access specification.

In step 518, the multi-tenant system provides the transformed second data to the target service. For example, as discussed above, the target service may be part of the central controller engine and/or it may be another service. In some embodiments, a common communication component (e.g., communication component 312) of the second service provider interface streams the transformed data to the target service.

FIG. 6 depicts a diagram 600 of an example of a computing device 602. Any of the systems, engines, datastores, and/or networks described herein may comprise an instance of one or more computing devices 602. In some embodiments, functionality of the computing device 602 is improved to the perform some or all of the functionality described herein. The computing device 602 comprises a processor 604, memory 606, storage 608, an input device 610, a communication network interface 612, and an output device 614 communicatively coupled to a communication channel 616. The processor 604 is configured to execute executable instructions (e.g., programs). In some embodiments, the processor 604 comprises circuitry or any processor capable of processing the executable instructions.

The memory 606 stores data. Some examples of memory 606 include storage devices, such as RAM, ROM, RAM cache, virtual memory, etc. In various embodiments, working data is stored within the memory 606. The data within the memory 606 may be cleared or ultimately transferred to the storage 608.

The storage 608 includes any storage configured to retrieve and store data. Some examples of the storage 608 include flash drives, hard drives, optical drives, cloud storage, and/or magnetic tape. Each of the memory system 606 and the storage system 608 comprises a computer-readable medium, which stores instructions or programs executable by processor 604.

The input device 610 is any device that inputs data (e.g., mouse and keyboard). The output device 614 outputs data (e.g., a speaker or display). It will be appreciated that the storage 608, input device 610, and output device 614 may be optional. For example, the routers/switchers may comprise the processor 604 and memory 606 as well as a device to receive and output data (e.g., the communication network interface 612 and/or the output device 614).

The communication network interface 612 may be coupled to a network (e.g., network 108) via the link 618. The communication network interface 612 may support communication over an Ethernet connection, a serial connection, a parallel connection, and/or an ATA connection. The communication network interface 612 may also support wireless communication (e.g., 802.11 a/b/g/n, WiMax, LTE, WiFi). It will be apparent that the communication network interface 612 may support many wired and wireless standards.

It will be appreciated that the hardware elements of the computing device 602 are not limited to those depicted in FIG. 6. A computing device 602 may comprise more or less hardware, software and/or firmware components than those depicted (e.g., drivers, operating systems, touch screens, biometric analyzers, and/or the like). Further, hardware elements may share functionality and still be within various embodiments described herein. In one example, encoding and/or decoding may be performed by the processor 604 and/or a co-processor located on a GPU (i.e., NVidia).

It will be appreciated that an “engine,” “system,” “datastore,” and/or “database” may comprise software, hardware, firmware, and/or circuitry. In one example, one or more software programs comprising instructions capable of being executable by a processor may perform one or more of the functions of the engines, datastores, databases, or systems described herein. In another example, circuitry may perform the same or similar functions. Alternative embodiments may comprise more, less, or functionally equivalent engines, systems, datastores, or databases, and still be within the scope of present embodiments. For example, the functionality of the various systems, engines, datastores, and/or databases may be combined or divided differently. The datastore or database may include cloud storage. It will further be appreciated that the term “or,” as used herein, may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance.

The datastores described herein may be any suitable structure (e.g., an active database, a relational database, a self-referential database, a table, a matrix, an array, a flat file, a documented-oriented storage system, a non-relational No-SQL system, and the like), and may be cloud-based or otherwise.

The systems, methods, engines, datastores, and/or databases described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented engines. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)).

The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented engines may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented engines may be distributed across a number of geographic locations.

Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.

The present invention(s) are described above with reference to example embodiments. It will be apparent to those skilled in the art that various modifications may be made and other embodiments may be used without departing from the broader scope of the present invention(s). Therefore, these and other variations upon the example embodiments are intended to be covered by the present invention(s). 

1. A computing system comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the computing system to perform: receiving, by a central controller engine, a user request to perform one or more operations associated with user data, the user data including first data and second data; sending a first request, by the central controller engine based on the user request, to a first service provider interface (SPI) associated with a first service, the first service being configured to operate on the first data in a first datastore, the first SPI including a first instance of a common interface component configured to facilitate communication between the central controller engine and the first SPI based on a uniform access specification, the first request being in a format associated with the uniform access specification, the first SPI including a first service interface component configured to communicate with the first service using a first internal specification; sending a second request, by the central controller engine based on the user request, to a second service provider interface (SPI) associated with a second service, the second service being configured to operate on the second data in a second datastore, the second SPI including a second instance of the common interface component configured to facilitate communication between the central controller engine and the second SPI based on the uniform access specification, the second request being in the format associated with the uniform access specification, the second SPI including a second service interface component configured to communicate with the second service using a second internal specification, the first internal specification being different than the second internal specification; obtaining, by the first service, at least a portion of the first data from the first datastore associated with the first service, the at least a portion of the first data being formatted according to the first internal specification; obtaining, by the second service, at least a portion of the second data from the second datastore associated with the second service, the at least a portion of the second data being formatted according to the second internal specification; transforming, by the first SPI, the at least a portion of the first data based on the uniform access specification, thereby generating transformed first data formatted according to the uniform access specification; transforming, by the second SPI, the at least a portion of the second data based on the uniform access specification, thereby generating transformed second data formatted according to the uniform access specification; providing, by the first instance of the common interface component of the first SPI, the transformed first data to a target service; and providing, by the second instance of the common interface component of the second SPI, the transformed second data to the target service.
 2. The computing system of claim 1, wherein the user data comprises tenant data, the first data comprises usage data, and the second data comprises subscription data.
 3. The computing system of claim 2, wherein the first service comprises a usage service, and the second service comprises a subscription service.
 4. The computing system of claim 1, wherein the central controller engine comprises a different service from the target service.
 5. The computing system of claim 1, wherein the central controller engine comprises the target service.
 6. The computing system of claim 1, wherein the instructions further cause the system to perform: storing, by the central controller engine, a first state of the first service and a second state of the second service.
 7. The computing system of claim 6, wherein the instructions further cause the system to perform: determining, by central controller engine, a failure of the first service; and relaunching, by the central controller engine in response to the determining the failure of the first service, the first service based on the stored first state of the first service.
 8. The system of claim 1, wherein the providing the transformed first data to the target service comprises: streaming, by the first instance of common communication component of the first SPI, the transformed first data to the target service; and wherein the providing the transformed second data to the target service comprises: streaming, by the second instance of common communication component of the second SPI, the transformed second data to the target service.
 9. A method implemented by a computing system including one or more physical processors and a storage medium storing machine-readable instructions, the method comprising: receiving, by a central controller engine, a user request to perform one or more operations associated with user data, the user data including first data and second data; sending a first request, by the central controller engine based on the user request, to a first service provider interface (SPI) associated with a first service, the first service being configured to operate on the first data in a first datastore, the first SPI including a first instance of a common interface component configured to facilitate communication between the central controller engine and the first SPI based on a uniform access specification, the first request being in a format associated with the uniform access specification, the first SPI including a first service interface component configured to communicate with the first service using a first internal specification; sending a second request, by the central controller engine based on the user request, to a second service provider interface (SPI) associated with a second service, the second service being configured to operate on the second data in a second datastore, the second SPI including a second instance of the common interface component configured to facilitate communication between the central controller engine and the second SPI based on the uniform access specification, the second request being in the format associated with the uniform access specification, the second SPI including a second service interface component configured to communicate with the second service using a second internal specification, the first internal specification being different than the second internal specification; obtaining, by the first service, at least a portion of the first data from the first datastore, the at least a portion of the first data being formatted according to the first internal specification; obtaining, by the second service, at least a portion of the second data from the second datastore, the at least a portion of the second data being formatted according to the second internal specification; transforming, by the first SPI, the at least a portion of the first data based on the uniform access specification, thereby generating transformed first data formatted according to the uniform access specification; transforming, by the second SPI, the at least a portion of the second data based on the uniform access specification, thereby generating transformed second data formatted according to the uniform access specification; providing, by the first instance of the common interface component of the first SPI, the transformed first data to a target service; and providing, by the second instance of the common interface component of the second SPI, the transformed second data to the target service.
 10. The method of claim 9, wherein the user data comprises tenant data, the first data comprises usage data, and the second data comprises subscription data.
 11. The method of claim 10, wherein the first service comprises a usage service, and the second service comprises a subscription service.
 12. The method of claim 9, wherein the central controller engine comprises a different service from the target service.
 13. The method of claim 9, wherein the central controller engine comprises the target service.
 14. The method of claim 9, further comprising: storing, by the central controller engine, a first state of the first service and a second state of the second service.
 15. The method of claim 14, further comprising: determining, by central controller engine, a failure of the first service; and relaunching, by the central controller engine in response to the determining the failure of the first service, the first service based on the stored first state of the first service.
 16. The method of claim 11, wherein the providing the transformed first data to the target service, comprises: streaming, by the first instance of common communication component of the first SPI, the transformed first data to the target service; and wherein the providing, by the second service, the transformed second data to the target service, comprises: streaming, by the second instance of common communication component of the second SPI, the transformed second data to the target service.
 17. A non-transitory computer readable medium comprising instructions that, when executed, cause one or more processors to perform: receiving, by a central controller engine, a user request to perform one or more operations associated with user data, the user data including first data and second data; sending a first request, by the central controller engine based on the user request, to a first service provider interface (SPI) associated with a first service, the first service being configured to operate on the first data in a first datastore, the first SPI including a first instance of a common interface component configured to facilitate communication between the central controller engine and the first SPI based on a uniform access specification, the first request being in a format associated with the uniform access specification, the first SPI including a first service interface component configured to communicate with the first service using a first internal specification; sending a second request, by the central controller engine based on the user request, to a second service provider interface (SPI) associated with a second service, the second service being configured to operate on the second data in a second datastore, the second SPI including a second instance of the common interface component configured to facilitate communication between the central controller engine and the second SPI based on the uniform access specification, the second request being in the format associated with the uniform access specification, the second SPI including a second service interface component configured to communicate with the second service using a second internal specification, the first internal specification being different than the second internal specification; obtaining, by the first service, at least a portion of the first data from the first datastore, the at least a portion of the first data being formatted according to the first internal specification; obtaining, by the second service, at least a portion of the second data from the second datastore, the at least a portion of the second data being formatted according to the second internal specification; transforming, by the first SPI, the at least a portion of the first data based on the uniform access specification, thereby generating transformed first data formatted according to the uniform access specification; transforming, by the second SPI, the at least a portion of the second data based on the uniform access specification, thereby generating transformed second data formatted according to the uniform access specification; providing, by the first instance of the common interface component of the first SPI, the transformed first data to a target service; and providing, by the second instance of the common interface component of the second SPI, the transformed second data to the target service. 